Repository navigation
chore: veo models pricing correction - #1028
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Replacing video_seconds with resolution-specific keys requires human validation because downstream billing compatibility and the new Veo 3.0 Fast rates cannot be verified from the supplied repository and pricing evidence.
No open issues 🎉
What changed in this PR
This PR corrects Veo model pricing in the Vertex AI pricing catalog and standardizes resolution-specific billing entries.
Changes:
- Corrects per-second prices for several Veo models.
- Replaces generic
video_secondskeys with resolution-specific duration keys. - Adds 1080p pricing entries where applicable while preserving default durations.
| File | Description |
|---|---|
pricing/vertex-ai.json |
Updates Veo rates and resolution-specific pricing entries. |
Review effort: Balanced
krishnachandra1709
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.